Finding Common Ground

For two decades, I've observed engineering projects succeed and fail – and more often than not, the technical aspects were not the primary determining factor. It was how well we navigated the human landscape – managing expectations, building trust, and, crucially, finding common ground with stakeholders.

Stakeholder management is often presented as a “soft skill,” but believe me, it's a core engineering leadership competency. It's the lubricant that keeps projects moving, fosters innovation, and prevents costly misunderstandings. And it starts with a deceptively simple principle: finding common ground.

The Problem: Differing Perspectives & Priorities

Engineering teams, by nature, are focused on how to build something. Product managers focus on what to build and why. Sales wants features that close deals now. Marketing needs a compelling narrative. Support is dealing with the fallout of current issues. Finance… well, they focus on the budget!

Each group has legitimate priorities, and those priorities often clash. When these differences aren’t addressed, you end up with:

• Scope creep: Endless requests that derail timelines and strain resources.
• Communication breakdowns: Misunderstandings that lead to rework and frustration.
• Lost momentum: Projects stalled by disagreements and a lack of alignment.
• Resentment: Teams feeling unheard or undervalued.

It’s easy to fall into the trap of viewing these differing viewpoints as obstacles. But what if you shifted your perspective and saw them as opportunities?

Beyond “Win-Win”: The Power of Shared Values

Forget the cheesy “win-win” negotiations. Finding common ground isn't about compromise; it's about uncovering shared values and building from there.

Here’s how I approach it, framed as a three-step process:

1. Understand Their “Why”: Before you dive into technical details or project timelines, take the time to understand why each stakeholder cares about a particular outcome. Don’t just listen to what they’re saying; dig deeper to understand the underlying motivations.

• Example: Sales is pushing for a new integration. Instead of thinking, "Another feature to build," ask, "What customer pain point does this solve? What revenue impact are you expecting?" Imagine a scenario: after probing, you discover they're facing a competitive threat, and the integration is crucial to retaining a key account facing a potential loss. Understanding that immediately reframes the conversation – it's no longer just a feature request, it’s a critical component of a revenue-saving initiative.

2. Translate Technical Details into Business Value: Engineers often speak in technical jargon, which can alienate non-technical stakeholders. The key is to translate those details into business outcomes.

• Instead of: “We need to refactor the authentication service to improve scalability.”
• Try: “Refactoring the authentication service will allow us to handle 10x more users, which will support the projected growth in the next quarter and prevent performance issues that could impact customer satisfaction.” Consider also quantifying the impact: “This refactor will support an anticipated 20% increase in user registrations next quarter, mitigating potential revenue loss from slow load times.”

3. Focus on the User: The user is often the ultimate common ground. Remind everyone that the goal is to create something valuable for the end user. Bring user research, usability testing results, and customer feedback into the conversation.

• Framework Suggestion: I often use a simple “User Story Mapping” workshop to visually represent the user journey and highlight areas where different stakeholders can contribute. User Story Mapping is a collaborative exercise where you map out the steps a user takes to achieve a goal. By visually representing the user journey, it becomes easier for everyone – technical and non-technical – to understand the impact of different features and identify areas for collaboration. This fosters empathy and shared understanding and ensures everyone is aligned on delivering value to the user.

A Framework for Difficult Conversations

Sometimes, despite your best efforts, you'll encounter resistance or conflict. Here's a framework I've found helpful, built on principles of active listening and solution-focused communication:

• Active Listening: Truly listen to understand their perspective, not just to formulate your response. Repeat back what you’ve heard to ensure understanding.
• Acknowledge Their Concerns: Validate their feelings, even if you don't agree with their position. ("I understand your concern about the timeline. It's important to get this right.")
• Seek Clarification: Ask open-ended questions to ensure you understand their reasoning. ("Can you help me understand why this is a priority for your team?")
• Focus on Solutions, Not Blame: Instead of dwelling on past mistakes, focus on finding a path forward. ("What can we do together to address this challenge?")

These principles aren’t just for during conflict; integrate them into all your stakeholder interactions. Regularly check in with stakeholders to understand their needs and address concerns before they escalate into conflicts.

Beyond Project Success: Building Trust

Finding common ground isn't just about getting projects done; it's about building trust and fostering long-term relationships. When stakeholders feel heard, respected, and valued, they're more likely to collaborate effectively and support your team's efforts.

I've seen teams thrive, not because they were the most technically brilliant, but because they invested in building strong relationships with their stakeholders. They understood that success wasn't just about delivering features; it was about creating a shared vision and working together to achieve it. As Peter Drucker, a renowned management theorist, once wrote, “Management is doing things right; leadership is doing the right thing.” Prioritizing relationships is a key component of leadership, and essential for long-term success.

Ultimately, remember that methodologies work if everyone prioritizes the benefit of others. This is true in stakeholder management too. Finding common ground isn’t about influence; it’s about empathy, understanding, and genuinely caring about the success of everyone involved.

What’s one stakeholder relationship you can proactively invest in this week?